Power headroom report generation

ABSTRACT

Apparatuses, methods, and systems are disclosed for power headroom report generation. One method includes aggregating multiple serving cells. The method includes determining that a power headroom report is triggered. The method includes receiving, at a first time after the power headroom report is triggered, a first uplink grant that allocates resources for a new transmission on a serving cell of the multiple serving cells. The method includes determining a power headroom value for each serving cell of the multiple serving cells being activated based on information received prior to and including the first time. The method includes generating a power headroom report medium access control control element including at least the power headroom value for each serving cell of the multiple serving cells being activated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No.62/558,433 entitled “POWER HEADROOM ELEMENT FORMATTING” and filed onSep. 14, 2017 for Joachim Lohr, which is incorporated herein byreference in its entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to power headroom reportgeneration.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Positive-Acknowledgment (“ACK”), AccessPoint (“AP”), Binary Phase Shift Keying (“BPSK”), Buffer Status Report(“BSR”), Clear Channel Assessment (“CCA”), Code Division Multiple Access(“CDMA”), Control Element (“CE”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“CSI”), CommonSearch Space (“CSS”), Control Resource Set (“CORESET”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Downlink Pilot Time Slot (“DwPTS”), Enhanced ClearChannel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), EvolvedNode B (“eNB”), European Telecommunications Standards Institute(“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex(“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency DivisionOrthogonal Cover Code (“FD-OCC”), General Packet Radio Services(“GPRS”), Guard Period (“GP”), Global System for Mobile Communications(“GSM”), Hybrid Automatic Repeat Request (“HARQ”), International MobileTelecommunications (“IMT”), Internet-of-Things (“IoT”), Layer 2 (“L2”),Licensed Assisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical ChannelPrioritization (“LCP”), Long Term Evolution (“LTE”), Multiple Access(“MA”), Medium Access Control (“MAC”), Multimedia Broadcast MulticastServices (“MBMS”), Modulation Coding Scheme (“MCS”), Machine TypeCommunication (“MTC”), massive MTC (“mMTC”), Multiple Input MultipleOutput (“MIMO”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”),Orthogonal Frequency Division Multiplexing (“OFDM”), Primary Cell(“PCell”), Physical Broadcast Channel (“PBCH”), Physical DownlinkControl Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”),Physical Downlink Shared Channel (“PDSCH”), Pattern Division MultipleAccess (“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”), PowerHeadroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”),Physical Random Access Channel (“PRACH”), Physical Resource Block(“PRB”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Radio Access Network (“RAN”), Radio ResourceControl (“RRC”), Random Access Procedure (“RACH”), Random AccessResponse (“RAR”), Radio Link Control (“RLC”), Radio Network TemporaryIdentifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum SystemInformation (“RMSI”), Resource Spread Multiple Access (“RSMA”),Reference Signal Received Power (“RSRP”), Round Trip Time (“RTT”),Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request(“SR”), Sounding Reference Signal (“SRS”), Single Carrier FrequencyDivision Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), SharedChannel (“SCH”), Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Synchronization Signal (“SS”), Transport Block (“TB”),Transport Block Size (“TBS”), Time-Division Duplex (“TDD”), TimeDivision Multiplex (“TDM”), Time Division Orthogonal Cover Code(“TD-OCC”), Transmission Time Interval (“TTI”), Transmit (“TX”), UplinkControl Information (“UCI”), User Entity/Equipment (Mobile Terminal)(“UE”), Uplink (“UL”), Universal Mobile Telecommunications System(“UMTS”), Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability andLow-latency Communications (“URLLC”), and Worldwide Interoperability forMicrowave Access (“WiMAX”).

In certain wireless communications networks, power headroom reports maybe used. In such networks, power headroom reports may include variousinformation.

BRIEF SUMMARY

Methods for power headroom report generation are disclosed. Apparatusesand systems also perform the functions of the apparatus. One embodimentof a method includes aggregating multiple serving cells. In someembodiments, the method includes determining that a power headroomreport is triggered. In certain embodiments, the method includesreceiving, at a first time after the power headroom report is triggered,a first uplink grant that allocates resources for a new transmission ona serving cell of the multiple serving cells. In various embodiments,the method includes determining a power headroom value for each servingcell of the multiple serving cells being activated based on informationreceived prior to and including the first time. In one embodiment, themethod includes generating a power headroom report medium access controlcontrol element including at least the power headroom value for eachserving cell of the multiple serving cells being activated.

One apparatus for power headroom report generation includes a processorthat: aggregates multiple serving cells; and determines that a powerheadroom report is triggered. In certain embodiments, the apparatusincludes a receiver that receives, at a first time after the powerheadroom report is triggered, a first uplink grant that allocatesresources for a new transmission on a serving cell of the multipleserving cells. In various embodiments, the processor: determines a powerheadroom value for each serving cell of the multiple serving cells beingactivated based on information received prior to and including the firsttime; and generates a power headroom report medium access controlcontrol element including at least the power headroom value for eachserving cell of the multiple serving cells being activated.

One method for power headroom report generation includes receiving apower headroom report medium access control control element including apower headroom for each serving cell of multiple serving cells beingactivated. In such embodiments, the power headroom for a correspondingservice cell is real or virtual.

One apparatus for power headroom report generation includes a receiverthat receives a power headroom report medium access control controlelement including a power headroom for each serving cell of multipleserving cells being activated. In such embodiments, the power headroomfor a corresponding service cell is real or virtual.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for power headroom report generationand/or reception;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for power headroom report generation;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for power headroom report reception;

FIG. 4 is a schematic block diagram illustrating one embodiment oftiming of multiple serving cells used for power headroom reportgeneration;

FIG. 5 is a schematic block diagram illustrating one embodiment of apower headroom report;

FIG. 6 is a schematic block diagram illustrating another embodiment of apower headroom report;

FIG. 7 is a flow chart diagram illustrating one embodiment of a methodfor power headroom report generation; and

FIG. 8 is a flow chart diagram illustrating one embodiment of a methodfor power headroom report reception.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forpower headroom report generation and/or reception. In one embodiment,the wireless communication system 100 includes remote units 102 andnetwork units 104. Even though a specific number of remote units 102 andnetwork units 104 are depicted in FIG. 1, one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may be used for power headroomreport generation. The remote unit 102 may aggregate multiple servingcells. In some embodiments, the remote unit 102 may determine that apower headroom report is triggered. In certain embodiments, the remoteunit 102 may receive, at a first time after the power headroom report istriggered, a first uplink grant that allocates resources for atransmission (e.g., new transmission) on a serving cell of the multipleserving cells. In various embodiments, the remote unit 102 may determinea power headroom value for each serving cell of the multiple servingcells being activated based on information received prior to andincluding the first time. In one embodiment, the remote unit 102 maygenerate a power headroom report medium access control control elementincluding at least the power headroom value for each serving cell of themultiple serving cells being activated. In some embodiments, the remoteunit 102 may transmit the power headroom report medium access controlcontrol element on the resources allocated by the first uplink grant.Accordingly, the remote unit 102 may be used for power headroom reportgeneration.

In certain embodiments, a network unit 104 may be used for powerheadroom report reception. In some embodiments, the network unit 104 mayreceive a power headroom report medium access control control elementincluding a power headroom for each serving cell of multiple servingcells being activated. In such embodiments, the power headroom for acorresponding service cell is real or virtual. Accordingly, the networkunit 104 may be used for power headroom report reception.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forpower headroom report generation. The apparatus 200 includes oneembodiment of the remote unit 102. Furthermore, the remote unit 102 mayinclude a processor 202, a memory 204, an input device 206, a display208, a transmitter 210, and a receiver 212. In some embodiments, theinput device 206 and the display 208 are combined into a single device,such as a touchscreen. In certain embodiments, the remote unit 102 maynot include any input device 206 and/or display 208. In variousembodiments, the remote unit 102 may include one or more of theprocessor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 may: aggregate multiple servingcells; and determine that a power headroom report is triggered. Incertain embodiments, the processor 202 may: determine a power headroomvalue for each serving cell of multiple serving cells being activatedbased on information received prior to and including a first time; andgenerate a power headroom report medium access control control elementincluding at least a power headroom value for each serving cell of themultiple serving cells being activated. The processor 202 iscommunicatively coupled to the memory 204, the input device 206, thedisplay 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the receiver 212 receives, at a first time after apower headroom report is triggered, a first uplink grant that allocatesresources for a transmission (e.g., a new transmission) on a servingcell of multiple serving cells. In certain embodiments, the transmitter210 transmits a power headroom report medium access control controlelement on the resources allocated by a first uplink grant. Althoughonly one transmitter 210 and one receiver 212 are illustrated, theremote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forpower headroom report reception. The apparatus 300 includes oneembodiment of the network unit 104. Furthermore, the network unit 104may include a processor 302, a memory 304, an input device 306, adisplay 308, a transmitter 310, and a receiver 312. As may beappreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In certain embodiments, the receiver 312 may receive a power headroomreport medium access control control element including a power headroomfor each serving cell of multiple serving cells being activated. In suchembodiments, the power headroom for a corresponding service cell is realor virtual. Although only one transmitter 310 and one receiver 312 areillustrated, the network unit 104 may have any suitable number oftransmitters 310 and receivers 312. The transmitter 310 and the receiver312 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 310 and the receiver 312 may be part of atransceiver.

To support various services (e.g., eMBB, URLLC, mMTC), 5G/NR may supportdifferent OFDM numerologies (e.g., SCS, CP length) in a singleframework. As may be appreciated, various configurations for NR may havediverse requirements in terms of data rates, latency, and/or coverage.For example, eMBB may support certain data rates (e.g., 20 Gbps fordownlink and 10 Gbps for uplink) and user-experienced data rates threetimes as much as is provided by IMT-Advanced systems. On the other hand,with URLLC, tighter requirements may be put on ultra-low latency (e.g.,0.5 ms for UL and DL each for user plane latency) and high reliability(e.g., 1-10⁻⁵ within 1 ms). Moreover, mMTC may use high connectiondensity, large coverage in harsh environments, and an extremelylong-life battery for low cost devices. Therefore, the OFDM numerology(e.g., SCS, OFDM symbol duration, CP duration, number of symbols perscheduling interval) that is suitable for one configuration may not workwell for another. For example, low-latency services may use a shortersymbol duration (and thus larger SCS) and/or fewer symbols perscheduling interval (e.g., TTI) than an mMTC service. Furthermore,configurations with large channel delay spreads may use a longer CPduration than scenarios with short delay spreads. In someconfigurations, the SCS may be optimized to facilitate a specific CPoverhead. In various embodiments, to support configurations in whichdifferent numerologies are applied across different carriers for a givenremote unit 102 as well as different numerologies within the samecarrier for a given remote unit 102, different OFDM numerologies may bemultiplexed in a frequency-domain and/or a time-domain within the samecarrier and/or across different carriers. This multiplexing mayfacilitate simultaneous support of services with vastly differentrequirements, e.g., ultra-low latency communications (short symbols andthus wide subcarrier spacing) and MBMS services (long symbols to enablelong cyclic prefix and thus narrow subcarrier spacing).

In LTE, a TTI and a subframe may both correspond to a same time durationof 1 ms. Moreover, both may refer to a 1 ms period associated withdifferent physical channels including a shortest possible intervalbetween two PDCCH occasions, the duration of the transmission of atransport block on PDSCH or PUSCH, or the time-domain schedulinggranularity. For NR however, a PDSCH or PUSCH duration for transmissionof a transport block may vary between a mini-slot, a slot, or multipleslots. In addition, in some embodiments, a remote unit 102 may beconfigured to monitor a DL control channel in terms of slot or OFDMsymbol with respect to a numerology of the DL control channel.Therefore, a remote unit 102 may be configured to monitor PDCCH on PDCCHmonitoring occasions once every number of slots (e.g., on a subset ofPDCCH monitoring candidates).

As used herein, TTI may refer to a time period (e.g., one or more OFDMsymbols or slot) for which a remote unit 102 is configured to monitor adownlink control channel, a time period for which a remote unit 102 isconfigured to monitor PDCCH (on a specific CORESET), and/or a durationof a data transmission on PDSCH and/or PUSCH.

In various embodiments, to aggregate multiple serving cells and/orcomponent carriers with different numerologies in NR, PHRs may be used.In some embodiments, a PHR may only be reported for activated servingcells with a configured uplink.

In LTE, a remote unit 102 may report an extended PHR for configurationsincluding carrier aggregation (e.g., PH info for each activated servingcell with configured uplink may be included in a PH MAC CE). As may beappreciated, because a TTI length in LTE may be the same for allcarriers, a PHR subframe (e.g., TTI which the PH information refers to)may be aligned across all component carriers and/or serving cells.

In NR, due to its support of different numerologies, a TTI of onecomponent carrier and/or serving cell may overlap with multiple TTIs ofanother carrier (e.g., a TTI of eMBB on one carrier may overlap with aTTI of URLLC on another carrier). In some embodiments, a network unit104 that receives an extended PHR may not be aware of which TTI areported PH information refers to. For example, in a configuration inwhich an extended PHR report is triggered and subsequently transmittedin a TTI, which overlaps multiple TTIs on a different carrier, a networkunit 104 may not know which of the overlapped TTI is a reference for thePH calculation. Accordingly, the network unit 104 may base its futurescheduling decisions on wrong assumptions (e.g., how close a remote unit102 is operating on a power limit) which may lead to power scalingissues and/or under-utilization of resources.

In various embodiments, PHR in NR may have issues related to a size of a(extended) PHR MAC CE, i.e. PHR MAC CE containing power headroominformation for multiple activated serving cells with configured uplink.Specifically, because NR may be used for very high data rate and lowlatency, a processing time available for both a transmitter and areceiver may be limited (e.g., for generating and/or decoding a TB).Therefore, L2 protocol functions for NR may be designed in aprocessing-power-friendly way. One example of this may be not supportingconcatenation of data segments in an RLC layer. Not supportingconcatenation of data segments in the RLC layer may enablepre-processing of both an RLC layer and a MAC layer before receiving anUL grant (e.g., PDCP SDU may be pre-constructed to MAC SDU with its ownMAC sub-header). Regarding the placement of MAC CEs, in variousembodiments, UL MAC CEs may be placed at the end of a TB before anypotential padding. This may be so that a transmitter may immediatelystart feeding part of the TB to PHY as soon as an UL grant is received.In configurations in which a MAC CE is placed at a beginning of a TB, atransmitter may need to wait until the MAC CE content is generatedbefore the channel coding can start. In some embodiments, a computationof a BSR and PHR MAC CE may be done at a later point of time becauseboth reflect a latest status before transmission (e.g., BSR may only becalculate after LCP has been finalized).

Because a size of an extended PHR MAC CE may not be fixed but may dependon a number of activated serving cells (with configured uplink) and alsomay depend on whether virtual or real PH is reported for a serving cell(Pcmax,c is not reported for a virtual PHR), generation of a TB from aprocessing timing perspective may be challenging for NR forconfigurations in which an extended PHR MAC CE is multiplexed in a TB.In certain embodiments, to generate a TB (e.g., during LCP) because MACCEs are generally prioritized over data channels, a remote unit 102 mayfirst reserve sufficient space within a TB for MAC CEs before assigningdata to logical channels (e.g., data radio bearers). In variousembodiments, in response to a size of MAC CEs only being known at a latepoint of time, an LCP procedure may be delayed. In certain embodiments,to determine a size of an extended PHR MAC CE for NR (e.g., at a time inwhich a remote unit 102 is aggregating multiple serving cells withdifferent numerologies and/or TTI lengths), the remote unit 102 maydetermine whether a virtual uplink transmission or a real uplinktransmission takes place on the serving cells in the TTI for which PH isreported. However, in some embodiments, for NR at a time in whichdifferent numerologies with different TTI length and/or timing relationsare used on serving cells, a remote unit 102 may not know immediately(e.g., upon having received an UL grant) whether PH information forserving cells is calculated based on actual or virtual uplinktransmission. Moreover, in certain embodiments, a size of a PHR MAC CEmay not be known immediately, which may also mean that LCP may not bestarted immediately upon having received an UL grant.

In some embodiments, for configurations in which a remote unit 102aggregates multiple NR component carriers and/or serving cells in orderto be able to start an LCP procedure immediately upon having received anUL grant, the remote unit 102 may determine a size of an extended PHRMAC CE immediately upon having received an UL grant.

In one embodiment, a remote unit 102 may determine a size of an extendedPHR MAC CE based on UL resource allocations, e.g., UL grants, receivedup until a point of time in which the remote unit 102 performs LCP. Tobe more specific, at a time in which a remote unit 102 receives an ULgrant in TTI N and at least one PHR has been triggered, the remote unit102 may consider all UL grants received for other activated servingcells, respectively UL component carriers, until and including TTI N fordetermining a size of the extended PHR MAC CE (e.g., for determiningwhether a PH value for a serving cell is determined based on real orvirtual uplink transmission).

In various embodiments, a remote unit 102 may ignore any uplink grantsscheduling an uplink transmission on the other activated serving cell inthe TTI in which a PHR MAC CE is transmitted which is received laterthan TTI N for a determination of the PH information. Therefore, incertain embodiments, a remote unit 102 may determine at TTI N (uponhaving received an UL grant in TTI N which schedules an initial PUSCHtransmission in TTI N+x including a (extended) PHR MAC CE) that avirtual PH will be computed for a serving cell (e.g., no uplinktransmission takes place on that serving cell in a PHR referencesubframe). In such embodiments, the remote unit 102 may report a virtualPHR for that serving cell even if an uplink transmission will bescheduled at a later point of time in the PHR reference subframe forthat serving cell. As used herein, a PHR reference subframe,respectively PHR reference TTI, may refer to a specific subframe/TTIthat is used as a reference point for a PHR. In other words, informationin the PHR may be relative to a specific subframe/TTI (i.e., the PHRreference subframe). For example, in FIG. 4, subframes I and S are PHRreference subframes.

As may be appreciated, considering only UL grants for active servingcells received until and including a TTI in which an UL grant schedulinguplink resources for transmission of an extended PHR MAC CE has beenreceived enables a remote unit 102 to determine a size of the extendedPHR MAC CE immediately (e.g., like in LTE), which in turn enables theremote unit 102 to start a TB generation process immediately (e.g., byperforming an LCP procedure).

FIG. 4 is a schematic block diagram illustrating one embodiment oftiming 400 of multiple serving cells used for power headroom reportgeneration. A first serving cell 402 (or carrier), a second serving cell404 (or carrier), and a third serving cell 406 (or carrier) areillustrated.

In some embodiments, a remote unit 102 is configured with 3 componentcarriers and/or serving cells (in which are all 3 activated), each ofthem having a different numerology and/or TTI/slot length. In theillustrated embodiment of FIG. 4, the remote unit 102 is configured withthe first serving cell 402, the second serving cell 404, and the thirdserving cell 406. In certain embodiments, PHR may be triggered before afirst time 408 (“t₀”) (e.g., during TTI_(N-3) on the first serving cell402) based on a predetermined criteria, and an extended PHR MAC CE maybe transmitted in TTI_(N) on the first serving cell 402 based on an ULgrant received at t₀ in TTI N−2.

Upon receiving an UL grant at t₀ (TTI N−2 on the first serving cell 402)for the PHR reporting subframe N, the remote unit 102 may start with anLCP procedure in order to generate the TB. As may be appreciated, todetermine a MAC SDU size of an LCH, a remote unit 102 may need to know asize of a PHR MAC CE (or extended PHR (“ePHR”) MAC CE). However, becausepotential UL grants for a PHR reference subframe on the second servingcell 404 and the third serving cell 406 are received at a later point intime (e.g., at a second time 410 “t₁” and at a third time 412 “t₂”respectively), a remote unit 102 may not be able to determine at to(e.g., TTI N−2) whether uplink transmissions take place on the secondand third serving cells 404 and 406 in the PHR reference subframe (e.g.,subframes I and S respectively). Therefore, the remote unit 102 may needto delay the LCP procedure, which might make it difficult to finalizegeneration of a TB (e.g., physical channel coding).

FIG. 5 is a schematic block diagram illustrating one embodiment of apower headroom report 500. In one embodiment, the power headroom report500 may include a first PH value, a second PH value, and a third PHvalue. One or more of the PH values may be real (e.g., actual) PH valuesand/or one or more of the PH values may be virtual (e.g., calculated,estimated, etc.).

FIG. 6 is a schematic block diagram illustrating another embodiment of apower headroom report 600. In one embodiment, the power headroom report600 may include a first PH value, a first v-field, a second PH value, asecond v-field, a third PH value, and a third v-field. One or more ofthe PH values may be real (e.g., actual) PH values and/or one or more ofthe PH values may be virtual (e.g., calculated, estimated, etc.). Thefirst v-field may correspond to the first PH value, the second v-fieldmay correspond to the second PH value, and the third v-field maycorrespond to the third PH value. The v-field may indicate whether itscorresponding PH value is real or virtual. For example, in oneembodiment, the v-field may be one bit in which a logic “0” indicatesthat the corresponding PH value is real, and a logic “1” indicates thatthe corresponding PH value is virtual. In another embodiment, thev-field may be one bit in which a logic “1” indicates that thecorresponding PH value is real, and a logic “0” indicates that thecorresponding PH value is virtual.

Returning to FIG. 4, in some embodiments, a remote unit 102 may onlyconsider UL grants received for activated component carriers and/orserving cells until and including to (e.g., UL grants received until andincluding TTI N−2) to facilitate determining a size of an extended PHRMAC CE. Therefore, the remote unit 102 may determine at to that avirtual PH value is to be computed and reported for the second servingcell 404 and the third serving cell 406, even if real uplinktransmissions are to take place in a PH reference subframe (e.g., TTI iis the PHR reference subframe for the second serving cell scheduled inTTI i−2 on the second serving cell 404 and TTI s is the PHR referencesubframe for the third serving cell scheduled in TTI s−2 on the thirdserving cell 406). In certain embodiments, a remote unit 102 may setfield values of an extended PHR MAC CE based on a reception status at t₀(e.g., the remote unit 102 sets a V-field for the second serving cell404 and the third serving cell 406 to 1 indicating that the PH Value isbased on a reference format (virtual PH)). In embodiments in which theV-field indicates a virtual PH, no P_(CMAX,c) field may be reported forthe second serving cell 404 and the third serving cell 406. Moreover, insuch embodiments, the MAC may indicate to PHY that a virtual PH valueshould be calculated for the second serving cell 404 and the thirdserving cell 406.

In various embodiments, a remote unit 102 may determine a size of atriggered (e.g., extended) PHR MAC CE by considering only UL grants aswell as transmissions on a PUCCH and grant-free uplink transmissions onactivated serving cells until a predetermined time (e.g., reception ofan UL grant which in turn triggers LCP procedure). By using theillustration of FIG. 4 for one example, a remote unit 102 may considerall UL grants received until to as well as a remote unit's 102 knowledgeand/or status at to regarding grant-free uplink transmissions and PUCCHtransmissions occurring in PHR reference subframes on the activatedserving cells/carrier for determining the size of a PHR MAC CE.

In some embodiments, a P_(CMAX,c) field may not be included in anextended PHR MAC CE for a serving cell and/or a component carrier in anembodiment in which a PH value is based on a reference format (e.g.,virtual PH). This may be because the P_(CMAX,c) value for a virtual PHis known by a network unit 104 and doesn't need to be reported, therebyreducing signaling overhead. In certain embodiments, a remote unit 102may always include a P_(CMAX,c) field for an activated serving cell inan extended PHR MAC CE, even for embodiments in which a PH value for aserving cell is based on a reference format (e.g., virtual PH). Suchembodiments may enable a remote unit 102 to know a size of an extendedPHR MAC CE immediately upon having received an UL grant and therebyenables a remote unit 102 to start a TB generation process immediately(e.g., by performing LCP). In some embodiments, a remote unit 102 may beenabled to report a PH value according to an uplink transmission statusin a PHR reference subframe and a V-flag may be set according to thetransmitted PH information (e.g., virtual or real). In certainembodiments, a remote unit 102 may include the P_(CMAX,c) field for thefirst serving cell 402, the second serving cell 404, and the thirdserving cell 406 in an extended PHR MAC CE. In some embodiments,processing power capabilities may enable a remote unit 102 to consideran UL grant received at t₁ for the second serving cell 404 for thegeneration of a TB scheduled at to. In such embodiments, the remote unit102 may report a real PH (e.g., with V-flag set to 0) for the secondserving cell 404 in the extended PHR MAC CE. In such embodiments, forthe third serving cell 406, the remote unit 102 may report a virtual PHR(e.g., V-flag set to 1).

In various embodiments, a remote unit 102 may determine a size of atriggered (e.g., extended) PHR MAC CE by considering UL grants as wellas transmissions on a PUCCH and grant-free uplink transmissions onactivated serving cells until a defined time instance (e.g., receptionof UL grant which in turn triggers LCP procedure). In some embodiments,a remote unit 102 may consider all UL grants received until to as wellas the remote unit's 102 knowledge and/or status at to regardinggrant-free uplink transmissions and PUCCH transmissions in PHR referencesubframes for determining the size of a PHR MAC CE.

In various embodiments, a remote unit 102 may decide at to (e.g., uponhaving received an UL grant on the first serving cell 402) to report avirtual PH value for the second serving cell 404 and the third servingcell 406 (e.g., because, according to the grant reception status at to,no uplink transmissions take place in the reference PHR subframes on thesecond serving cell 404 and the third serving cell 406). In someembodiments, in addition to an extended PHR MAC transmitted on the firstserving cell 402, a remote unit 102 transmits a PHR MAC CE for thesecond serving cell 404 in a next uplink transmission taking place onthe second serving cell 404 (e.g., in a PHR reference subframe), andtransmits a PHR MAC CE for the third serving cell 406 in a next uplinktransmission on the third serving cell 406. This may be because for boththe second and third serving cells 404 and 406 only a virtual PHR isreported in the extended PHR MAC CE sent on the first serving cell 402.In such embodiments, the additional PHR MAC CEs may provide the networkunit 104 with more detailed information about a remote unit's 102 powersituation for the serving cells than what is conveyed with a virtualPHR.

In various embodiments, to support multiple open loop power controlparameters a network unit 104 may configure multiple P₀ and/or α values(e.g., for specific combinations of one or more beams, UL waveforms,and/or service types). In certain embodiments, the network unit 104 mayconfigure different power control parameters for URLLC and eMBB becauseboth services have different QoS requirements. In some embodiments, fora PHR calculated based on a reference transmission and/or format (e.g.,virtual PH), a network unit 104 may be aware of which uplink powercontrol parameters a remote unit 102 uses for a virtual PHR calculationin order to interpret the received PH information correctly. Therefore,a predefined set of power control parameters (e.g., P₀, P_(O_PUSCH,c)and/or alpha value) may be used for calculation of a virtual PH.

In certain embodiments in which a network unit 104 configures multiplepower control parameters, (e.g., multiple pairs of P₀ and α) a remoteunit 102 may use a first number of power control parameters of a set ofconfigured power control parameters for a calculation of a virtual PHvalue. In some embodiments, a predefined TX beam or combination of beamsand/or a predefined numerology may be used for computation of a virtualPH value (e.g., the PH value may be based on a reference format).

In one embodiment, a network unit 104 may configure multiple (e.g., openloop) power control parameters (e.g., P₀ and α values) for differentservice types. In such an embodiment, during a time in which a remoteunit 102 performs logical channel multiplexing, (e.g., data of multipleLCHs is multiplexed in one TB) the remote unit 102 MAC may indicate aservice with a highest logical channel priority to a PHY layer containedin the TB (e.g., according to LCP procedure). In some embodiments, thePHY selects open loop power control parameters based on indicatedservices from a MAC.

In certain embodiments, a remote unit 102 power class for centimeterwave (“CMW”) and millimeter wave (“MMW”) (e.g., above 24 GHz) may beconsidered Effective Isotropic Radiated Power (“EIRP”). In someembodiments, for an antenna radiation pattern measurement, if a singlevalue of EIRP is given, this may be a maximum value of the EIRP over allmeasured angles. In certain embodiments, EIRP may be related to thepower transmitted from a radio/PA (“P_(t)”), cable losses (e.g.,possibly including antenna mismatch) “L”, and antenna gain (“G”) by thefollowing formula: EIRP=P_(t)−L+G.

In various embodiments, cable losses L may be neglected because they aregenerally a small fraction of a dB. In some embodiments, Pcmax may bedefined for above 24 GHz range in terms of EIRP that includes an antennabeam-forming gain. In certain RAN simulation assumptions, a remote unit102 RX beam-forming gain may be included in RSRP measurements and thusin a path-loss calculation. In certain embodiments, it may beanticipated that power control equations for NR may be similar to thoseused for LTE. For example UL output power in dBm for PUSCH may be:P_(PUSCH)=min {P_(cmax,c), (P_(0,PUSCH)+αPL)+10log(M_(PUSCH))+Δ_(other)+f_(c)(i)}.

In some embodiments, as the path loss value PL may consider remote unit102 RX beam-forming and/or antenna gain, there may be in a formula forthe UL output power (e.g., for PUSCH, PUCCH, and/or SRS) an additionalfactor which represents TX antenna gain. In one specific embodiment, adifference between RX and TX antenna gain may be used in a power controlformula. For embodiments in which RX and TX antenna gain are the same, afactor that represents TX antenna gain may be zero.

In certain embodiments, when computing a virtual PHR (e.g., PH valuebased on some reference format and/or transmission), a remote unit 102may assume that TX antenna gain and RX antenna gain are the same (e.g.,no correction factor may be considered). In another embodiment, apredefined TX antenna gain may be used for a computation of a virtualPHR (e.g., TX antenna gain and/or beam forming gain may be set to zerofor a determination of a P_(cmax) value and a corresponding PH value).

Various embodiments of extended PHR MAC CEs and corresponding fielddescriptions are described below.

C_(i): this field may indicate a presence of a PH field for an SCellwith SCellIndex i. In some embodiments, the C_(i) field set to “1” mayindicate that a PH field for the SCell with SCellIndex i is reported. Insuch embodiments, the C_(i) field set to “0” may indicate that a PHfield for an SCell with SCellIndex i is not reported.

R: this field may be for a reserved bit, and, in some embodiments, maybe set to “0”.

V: this field may indicate whether a PH value is based on a realtransmission or a reference format (e.g., virtual). For a Type 1 PH, V=0may indicate a real transmission on PUSCH and V=1 may indicate that aPUSCH reference format is used. For a Type 2 PH, V=0 may indicate a realtransmission on PUCCH and V=1 may indicate that a PUCCH reference formatis used. For a Type 3 PH, V=0 may indicate a real transmission on SRSand V=1 may indicate that an SRS reference format is used. Furthermore,for Type 1, Type 2, and Type 3 PH, V=0 may indicate a presence of anoctet containing an associated P_(CMAX,c) field, and V=1 may indicatethat the octet containing the associated P_(CMAX,c) field is omitted.

PH: this field may indicate a power headroom level. A length of thefield may be 6 bits.

P: this field may indicate whether a MAC entity applies power backoffdue to power management (e.g., as allowed by P-MPR_(c)). A MAC entitymay set P=1 if a corresponding P_(CMAX,c) field would have had adifferent value if no power backoff due to power management had beenapplied.

P_(CMAX,c): if present, this field may indicate the P_(CMAX,c) or {tildeover (P)}_(CMAX,c) used for calculation of the preceding PH field.

FIG. 7 is a flow chart diagram illustrating one embodiment of a method700 for power headroom report generation. In some embodiments, themethod 700 is performed by an apparatus, such as the remote unit 102. Incertain embodiments, the method 700 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 700 may include aggregating 702 multiple serving cells. Insome embodiments, the method 700 includes determining 704 that a powerheadroom report is triggered. In certain embodiments, the method 700includes receiving 706, at a first time after the power headroom reportis triggered, a first uplink grant that allocates resources for anuplink transmission (e.g., a new transmission) on a serving cell of themultiple serving cells. In various embodiments, the method 700 includesdetermining 708 a power headroom value for each serving cell of themultiple serving cells being activated based on information receivedprior to and including the first time. In one embodiment, the method 700includes generating 710 a power headroom report medium access controlcontrol element including at least the power headroom value for eachserving cell of the multiple serving cells being activated. In someembodiments, the method 700 includes transmitting 712 the power headroomreport medium access control control element on the resources allocatedby the first uplink grant.

In certain embodiments, the information includes uplink related downlinkcontrol information. In some embodiments, the information includes anuplink resource allocation for a configured grant. In variousembodiments, the first time corresponds to a physical downlink controlchannel occasion. In one embodiment, determining the power headroomvalue for each serving cell of the multiple serving cells beingactivated includes ignoring information received at a second time laterthan the first time.

In certain embodiments, determining the power headroom value for eachserving cell of the multiple serving cells being activated includesdetermining whether the power headroom value for each serving cell ofthe multiple serving cells being activated is based on a real uplinktransmission or a virtual uplink transmission. In some embodiments, thereal uplink transmissions includes a transmission based on a receiveduplink grant. In various embodiments, the virtual uplink transmissionincludes a virtual transmission based on a reference format.

In one embodiment, the power headroom report medium access controlcontrol element includes an indicator corresponding to each serving cellof the multiple serving cells being activated, and the indicatorindicates whether the power headroom value for a corresponding servingcell is real or virtual. In certain embodiments, the power headroomreport includes a power headroom corresponding to each serving cell ofthe multiple serving cells being activated, and the power headroom for acorresponding serving cell is real or virtual. In some embodiments, thepower headroom report is triggered in response to a timer expiring.

FIG. 8 is a flow chart diagram illustrating one embodiment of a method800 for power headroom report reception. In some embodiments, the method800 is performed by an apparatus, such as the network unit 104. Incertain embodiments, the method 800 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 800 may include receiving 802 a power headroom report mediumaccess control control element including a power headroom for eachserving cell of multiple serving cells being activated. In suchembodiments, the power headroom for a corresponding service cell is realor virtual.

In certain embodiments, the power headroom report medium access controlcontrol element includes an indicator corresponding to each serving cellof the multiple serving cells being activated, and the indicatorindicates whether the power headroom value for a corresponding servingcell is real or virtual. In some embodiments, the power headroom for acorresponding serving cell is real in response to a remote unit 102performing an uplink transmission according to an uplink grant on thecorresponding serving cell. In various embodiments, the power headroomfor a corresponding serving cell is virtual in response to a remote unitnot performing an uplink transmission on the serving cell according toan uplink grant.

In one embodiment, a method comprises: aggregating a plurality ofserving cells; determining that a power headroom report is triggered;receiving, at a first time after the power headroom report is triggered,a first uplink grant that allocates resources for a transmission (e.g.,a new transmission) on a serving cell of the plurality of serving cells;determining a power headroom value for each serving cell of theplurality of serving cells being activated based on information receivedprior to and including the first time; generating a power headroomreport medium access control control element comprising at least thepower headroom value for each serving cell of the plurality of servingcells being activated; and/or transmitting the power headroom reportmedium access control control element on the resources allocated by thefirst uplink grant.

In certain embodiments, the information comprises uplink relateddownlink control information.

In some embodiments, the information comprises an uplink resourceallocation for a configured grant.

In various embodiments, the first time corresponds to a physicaldownlink control channel occasion.

In one embodiment, determining the power headroom value for each servingcell of the plurality of serving cells being activated comprisesignoring information received at a second time later than the firsttime.

In certain embodiments, determining the power headroom value for eachserving cell of the plurality of serving cells being activated comprisesdetermining whether the power headroom value for each serving cell ofthe plurality of serving cells being activated is based on a real uplinktransmission or a virtual uplink transmission.

In some embodiments, the real uplink transmission comprises atransmission based on a received uplink grant.

In various embodiments, the virtual uplink transmission comprises avirtual transmission based on a reference format.

In one embodiment, the power headroom report medium access controlcontrol element comprises an indicator corresponding to each servingcell of the plurality of serving cells being activated, and theindicator indicates whether the power headroom value for a correspondingserving cell is real or virtual.

In certain embodiments, the power headroom report comprises a powerheadroom corresponding to each serving cell of the plurality of servingcells being activated, and the power headroom for a correspondingserving cell is real or virtual.

In some embodiments, the power headroom report is triggered in responseto a timer expiring.

In one embodiment, an apparatus comprises: a processor that: aggregatesa plurality of serving cells; and determines that a power headroomreport is triggered; a receiver that receives, at a first time after thepower headroom report is triggered, a first uplink grant that allocatesresources for a transmission (e.g., new transmission) on a serving cellof the plurality of serving cells; and/or a transmitter, wherein: theprocessor: determines a power headroom value for each serving cell ofthe plurality of serving cells being activated based on informationreceived prior to and including the first time; and generates a powerheadroom report medium access control control element comprising atleast the power headroom value for each serving cell of the plurality ofserving cells being activated; and/or the transmitter transmits thepower headroom report medium access control control element on theresources allocated by the first uplink grant.

In certain embodiments, the information comprises uplink relateddownlink control information.

In some embodiments, the information comprises an uplink resourceallocation for a configured grant.

In various embodiments, the first time corresponds to a physicaldownlink control channel occasion.

In one embodiment, the processor ignores downlink control informationallocating uplink resources received at a second time later than thefirst time for computation of the power headroom report.

In certain embodiments, the processor determines whether the powerheadroom value for each serving cell of the plurality of serving cellsbeing activated is based on a real uplink transmission or a virtualuplink transmission.

In some embodiments, the real uplink transmission comprises atransmission based on a received uplink grant.

In various embodiments, the virtual uplink transmission comprises avirtual transmission based on a reference format.

In one embodiment, the power headroom report medium access controlcontrol element comprises an indicator corresponding to each servingcell of the plurality of serving cells being activated, and theindicator indicates whether the power headroom value for a correspondingserving cell is real or virtual.

In certain embodiments, the power headroom report comprises a powerheadroom corresponding to each serving cell of the plurality of servingcells being activated, and the power headroom for a correspondingserving cell is real or virtual.

In some embodiments, the power headroom report is triggered in responseto a timer expiring.

In one embodiment, a method comprises: receiving a power headroom reportmedium access control control element comprising a power headroom foreach serving cell of a plurality of serving cells being activated,wherein the power headroom for a corresponding service cell is real orvirtual.

In certain embodiments, the power headroom report medium access controlcontrol element comprises an indicator corresponding to each servingcell of the plurality of serving cells being activated, and theindicator indicates whether the power headroom value for a correspondingserving cell is real or virtual.

In some embodiments, the power headroom for a corresponding serving cellis real in response to a remote unit performing an uplink transmissionaccording to an uplink grant on the corresponding serving cell.

In various embodiments, the power headroom for a corresponding servingcell is virtual in response to a remote unit not performing an uplinktransmission on the serving cell according to an uplink grant.

In one embodiment, an apparatus comprises: a receiver that receives apower headroom report medium access control control element comprising apower headroom for each serving cell of a plurality of serving cellsbeing activated, wherein the power headroom for a corresponding servicecell is real or virtual.

In certain embodiments, the power headroom report medium access controlcontrol element comprises an indicator corresponding to each servingcell of the plurality of serving cells being activated, and theindicator indicates whether the power headroom value for a correspondingserving cell is real or virtual.

In some embodiments, the power headroom for a corresponding serving cellis real in response to a remote unit performing an uplink transmissionaccording to an uplink grant on the corresponding serving cell.

In various embodiments, the power headroom for a corresponding servingcell is virtual in response to a remote unit not performing an uplinktransmission on the serving cell according to an uplink grant.

In one embodiment, a method includes: generating a power headroom reportmedium access control control element comprising at least a powerheadroom value for each serving cell of a plurality of serving cellsbeing activated; and transmitting the power headroom report mediumaccess control control element on resources allocated by a first uplinkgrant, wherein the power headroom value for at least one serving cell isa virtual power headroom value, and the virtual power headroom value isbased on a reference transmission format.

In some embodiments, a method for computing a virtual power headroomreport includes using predefined power control parameters from a set ofconfigured power control parameters. In such embodiments, the predefinedpower control parameters may include P₀, P_(O_PUSCH, c) alpha, or somecombination thereof. In certain embodiments, a method of computing avirtual power headroom report includes using the first configured powercontrol parameter of each of the predefined power control parametersfrom the set of configured power control parameters. In variousembodiments, a method for computing a virtual power headroom reportincludes using a predefined beam information for the computation of thevirtual power headroom report.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. A method comprising: aggregating aplurality of serving cells; determining that a power headroom report istriggered; receiving, at a first time after the power headroom report istriggered, a first uplink grant that allocates resources for a newtransmission on a first serving cell of the plurality of serving cells;determining a power headroom value for each serving cell of theplurality of serving cells being activated based on information receivedat a time prior to and including the first time; generating a powerheadroom report medium access control control element comprising atleast the power headroom value for each serving cell of the plurality ofserving cells being activated; and transmitting the power headroomreport medium access control control element on the uplink resourcesallocated by the uplink grant received at the first time.
 2. The methodof claim 1, wherein the information comprises uplink related downlinkcontrol information.
 3. The method of claim 1, wherein the informationcomprises an uplink resource allocation for a configured grant.
 4. Themethod of claim 1, wherein the first time corresponds to a physicaldownlink control channel occasion.
 5. The method of claim 1, whereindetermining the power headroom value for each serving cell of theplurality of serving cells comprises determining whether the powerheadroom value for each serving cell of the plurality of serving cellsbeing activated is based on a real uplink transmission or a virtualuplink transmission.
 6. The method of claim 1, wherein the powerheadroom report medium access control control element comprises anindicator corresponding to each serving cell of the plurality of servingcells being activated, and the indicator indicates whether the powerheadroom value for a corresponding serving cell is real or virtual. 7.The method of claim 1, wherein the power headroom report comprises apower headroom corresponding to each serving cell of the plurality ofserving cells being activated, and the power headroom for acorresponding serving cell is real or virtual.
 8. The method of claim 1,wherein the power headroom report is triggered in response to a timerexpiring.
 9. An apparatus comprising: a processor that: aggregates aplurality of serving cells; and determines that a power headroom reportis triggered; a receiver that receives, at a first time after the powerheadroom report is triggered, a first uplink grant that allocatesresources for a new transmission on a first serving cell of theplurality of serving cells, wherein: the processor: determines a powerheadroom value for each serving cell of the plurality of serving cellsbeing activated based on information received at a time prior to andincluding the first time; and generates a power headroom report mediumaccess control control element comprising at least the power headroomvalue for each serving cell of the plurality of serving cells beingactivated; and a transmitter that transmits the power headroom reportmedium access control control element on the uplink resources allocatedby the uplink grant received at the first time.
 10. The apparatus ofclaim 9, wherein the processor ignores downlink control informationallocating uplink resources received at a second time later than thefirst time for computation of the power headroom report.
 11. Theapparatus of claim 9, wherein the processor determines whether the powerheadroom value for each serving cell of the plurality of serving cellsbeing activated is based on a real uplink transmission or a virtualuplink transmission.
 12. The apparatus of claim 11, wherein the realuplink transmission comprises a transmission based on a received uplinkgrant.
 13. The apparatus of claim 11, wherein the virtual uplinktransmission comprises a virtual transmission based on a referenceformat.
 14. A method comprising: receiving a power headroom reportmedium access control control element comprising a power headroom foreach serving cell of a plurality of serving cells being activated,wherein the power headroom for a corresponding service cell is real orvirtual, the power headroom report medium access control control elementcomprises an indicator corresponding to each serving cell of theplurality of serving cells being activated, and the indicator indicatesvia a field value whether the power headroom value for a correspondingserving cell is real or virtual.
 15. The method of claim 14, wherein thepower headroom for a corresponding serving cell is real in response to aremote unit performing an uplink transmission according to an uplinkgrant on the corresponding serving cell.
 16. The method of claim 14,wherein the power headroom for a corresponding serving cell is virtualin response to a remote unit not performing an uplink transmission onthe serving cell according to an uplink grant.
 17. An apparatuscomprising: a receiver that receives a power headroom report mediumaccess control control element comprising a power headroom for eachserving cell of a plurality of serving cells being activated, whereinthe power headroom for a corresponding service cell is real or virtual,the power headroom report medium access control control elementcomprises an indicator corresponding to each serving cell of theplurality of serving cells being activated, and the indicator indicatesvia a field value whether the power headroom value for a correspondingserving cell is real or virtual.
 18. The apparatus of claim 17, whereinthe power headroom for a corresponding serving cell is real in responseto a remote unit performing an uplink transmission according to anuplink grant on the corresponding serving cell.